Skip to content

[AMD] perf-changelog: duplicate dsv4-fp4-mi355x-sglang TP4 fixed-seq-len entry#1795

Open
Oseltamivir wants to merge 3 commits into
mainfrom
dup/dsv4-fp4-mi355x-sglang-changelog
Open

[AMD] perf-changelog: duplicate dsv4-fp4-mi355x-sglang TP4 fixed-seq-len entry#1795
Oseltamivir wants to merge 3 commits into
mainfrom
dup/dsv4-fp4-mi355x-sglang-changelog

Conversation

@Oseltamivir

@Oseltamivir Oseltamivir commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

Duplicates the perf-changelog.yaml entry for dsv4-fp4-mi355x-sglang originally added in #1768. The duplicate entry is identical in content (config-keys, description, and pr-link).

Test plan

  • N/A — changelog-only change

Note

Low Risk
Changelog-only YAML append with no runtime or benchmark impact; the only downside is redundant history if consumers assume one entry per PR.

Overview
Appends a second perf-changelog.yaml block for dsv4-fp4-mi355x-sglang that matches the entry already recorded for PR #1762 (TP4 fixed-seq-len search space and expanded 8k1k sweeps). No new config keys, descriptions, or benchmark behavior—only a duplicate changelog record at the end of the file.

Reviewed by Cursor Bugbot for commit 5927254. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

If it is not, please create a PR first before we can merge your single node PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

PR authors are responsible for ensuring that after merging, all GitHub Action jobs fully pass. A lot of the time, failures are just flakes and simply re-running the failed jobs will fix it. If re-running failed jobs is attempted, PR authors are responsible for ensuring it passes. See GitHub's docs on re-running failed jobs: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

As a rule of thumb, generally, PR authors should request a review & get a PR approval from the respective companies' CODEOWNERS before requesting a review from core maintainers.

If additional help is needed, PR authors can reach out to core maintainers over Slack.

@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant